-
Notifications
You must be signed in to change notification settings - Fork 12
Integration of Flux as a wrapper engine #2708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…endency error The error occurred while executing "autosubmit run"
By now it is only functional with Slurm
It is pending to develop some remaining kinds of wrapper and incorporating error handling, retries, stat files...
…age builder Also added some clarifying comments for myself (marked as TODOs)
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #2708 +/- ##
==========================================
- Coverage 67.70% 67.48% -0.23%
==========================================
Files 86 88 +2
Lines 19786 19894 +108
Branches 3840 3860 +20
==========================================
+ Hits 13396 13425 +29
- Misses 5458 5533 +75
- Partials 932 936 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
374fbdd to
03c1cb0
Compare
Some parameters are now directly provided to "flux batch"
manuel-g-castro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall I am really happy with the implementation.
I find it very elegantly done, given the high degree of difficulty of the code base.
I made some minor comments here and there, but my major two comments regard the creation of the STAT files and a file to check if the wrapper failed in the horizontal-vertical case.
The first point could turn to be unnecessary if @kinow 's PR stops the creation of this file.
The second point is a suggestion just to avoid yet-another-file in the parallel file system.
Whenever I have time, I plan to install this branch and try the wrappers.
Thanks!
| {1} | ||
| # Instantiate Flux within the allocated resources and run the jobs | ||
| srun --cpu-bind=none flux start --verbose=2 /usr/bin/bash flux_runner.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to add a #TODO to parametrize the verbosity of Flux.
52ad1d7 to
84082ac
Compare
|
Hi, @manuel-g-castro! In commit 0823ab3 I introduce a new key to the Autosubmit wrapper configuration called This new parameter is optional and can be assigned to a wrapper global or locally. That is, you can set the Here is an example: WRAPPERS:
WRAPPER_SIM:
POLICY: "flexible"
MIN_WRAPPED: 1
MAX_WRAPPED: 6
TYPE: "vertical"
JOBS_IN_WRAPPER: "SIM"
METHOD: FLUX
CUSTOM_ENV_SETUP: |
module load miniconda
source /apps/GPP/MINICONDA/24.1.2/etc/profile.d/conda.sh
conda activate flux
conda infoI'm looking forward to know your experience loading the Spack package to see if Flux wrappers will work in any scenario. I have also uploaded my workflow for testing vertical wrappers with the Flux method to WorkflowHub (it is private and only users under the BSC-CES organization can access it), in case you want to make a quick test. |
Partially closes #2697
Check List
CONTRIBUTING.md.pyproject.toml.CHANGELOG.mdif this is a change that can affect users.Closes #1234).